Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-3714

Search function on customer portal page intermittently does not auto populate

      NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.

      Summary

      When searching in Customer Portal, modifying/deleting a previous keyword does not auto populate search results.

      Environment

      • Issue occurs in Firefox, Safari and Chrome, though the replication steps are slightly different. The issue is most obvious in Chrome.

      Steps to Reproduce

      1. Create a JSD project
      2. Link a Confluence space to the project in project settings and make sure customers can access space/project.
      3. Visit the customer portal page to your project and type in a search word. Notice that as you type, there is a spinning circle to indicate that the system is searching.
      4. Once the search results auto populate, backspace to delete the word.
      5. Begin typing in a new search word. If the search auto populates, complete steps 3-5 again, until you find that nothing populates or happens when you type in search words.

      Expected Results

      When typing in a search word in the customer portal, articles should auto populate or a message saying “No solutions found.” should appear (if nothing matches the search). The below screenshot shows an example of a search for a keyword that does not exist in the KB:

      If I delete the word MacBook, and try typing in a new search term, the portal should begin to auto populate responses to my new search term.

      Actual Results

      The first search works, however if you delete and try typing in a new word, nothing will populate. An example of this can be seen in the following screenshot:

      Depending upon which browser you’re using, you may need to delete and re-add keywords multiple times to replicate. In Chrome it happens typically after one time. In Safari and Firefox it can take up to 4 or 5 times of typing in a keyword, deleting, and adding a new word.
      Nothing is apparent in the logs, aside from the following:

      2016-04-26 20:05:36.501498500 2016-04-26 20:05:36,501 JIRA-EventThread-271 WARN rfuerst 1205x12718x1 1ekp03u 4.15.43.214 /servicedesk/customer/portal/2 [c.a.workcontext.api.WorkContextManager] Created WorkContext leniently (see: go/work-context-lenient-mode-errors) thread: JIRA-EventThread-271
      2016-04-26 20:05:37.419404500 2016-04-26 20:05:37,419 JIRA-EventThread-273 WARN rfuerst 1205x12718x1 1ekp03u 4.15.43.214 /servicedesk/customer/portal/2 [c.a.workcontext.api.WorkContextManager] Created WorkContext leniently (see: go/work-context-lenient-mode-errors) thread
      

      Development console does not show anything either:

      Workaround

      The current workaround is to completely reload the customer portal page and re-initiate a search.

        1. dev_console.png
          dev_console.png
          33 kB
        2. search_actual.png
          search_actual.png
          40 kB
        3. search_expected.png
          search_expected.png
          33 kB

            [JSDCLOUD-3714] Search function on customer portal page intermittently does not auto populate

            Closing this ticket due to the lack of activity

            Leonardo Diniz added a comment - Closing this ticket due to the lack of activity

            I was the one who first reported this. Note that about 2 weeks ago (let's say April 7th, 2016) this problem was not happening - and I had been doing a LOT of testing of your Help Desk (since we just rolled it out). Most of my use of Help Desk use/testing was via Chrome.

            Mark Kraatz added a comment - I was the one who first reported this. Note that about 2 weeks ago (let's say April 7th, 2016) this problem was not happening - and I had been doing a LOT of testing of your Help Desk (since we just rolled it out). Most of my use of Help Desk use/testing was via Chrome.

              ldiniz Leonardo Diniz
              rfuerst Rachel Fuerst (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: